2015-05-04 - 16728 - Spec - SNC Single Work Order #SNCProject #ABAPSNC
SPECIFICATIONS
2015-05-04 - 16728 - Spec - SNC Single Work Order Process.
Purpose
Create a Single Work Order in SNC per Purchase Order to minimize the user confirmation.
Admin Info
| Purpose |
SNC Single Work Order Process |
| Requested By |
Jeffery Mau |
| Spec Created By |
Adithya, Venkat |
| Spec Created Date |
05/07/2015 |
| Spec QA by |
Adithya, |
| Objects |
|
| Document Status |
Closed - This option is not used in the Simplified WO Process |
Estimates
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
08 |
| 2 |
Documentation |
|
| 3 |
Development/ Config |
112 |
| 4 |
Unit test in DEV |
40 |
| 5 |
Unit test in QUA |
|
| 6 |
Other activity |
|
| TOTAL |
160 |
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]Three Options were given for this requirement which are specified in the document attached below:
SCM - 2015-04-14 - 16728 - Spec - SNC Approach on Single Work Order Create for a PO
Documents
[Attach any document(s) received for the requirement(s)]
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]Currently Work Orders (WOs) are created at Purchase Order item level. This creates user and system issues that need to be addressed:
- High number of user confirmations required- If there are many lines in the PO, multiple WOs are created one per a PO Line.For example, : If a PO has 500 lines system creates 500 work orders then the user has to click 500 items for each phase of a WO.
- Confirmation Idocs fail and have to be manually reprocessed.
In Scope:
[List the activities to be included in scope]All POs sent to SNC only.
Out of Scope:
[Out of scope activities]Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
New Era would like to create a single work order (with 4 reporting phases) for the PO. Any statuses confirmed on this item would be updated on all other items of the ECC PO via a program. Unfortunately a single WO cannot be created at the header level. Therefore such a single WO would need to be created line level. There are the three options for line level WOs:
Out of the three options provided NE has chosen option 1 which is:
Users will confirm status on only one Active Item of the PO.
- The current WO list program will be replaced by a program to create only one Work list for the first active item.
- Statuses reported on this WO will be presumed to be for the ENTIRE PO.
- If the first active item is subsequently deleted in ECC, another Work list will be generated for reporting *** To be discussed. May not be required if no PO changes are allowed after Publish.
Test Plan
[List test scenarios/cases to be executed here]| Test ID |
Test Scenario |
Expected Results |
| SNC001 |
end to end cycle for order type NB without any line deletions. |
Outputs and document data match current multi WL process |
| SNC002 |
end to end cycle for order type NB without any line deletions for large POs |
Outputs and document data match current multi WL process |
| SNC003 |
end to end cycle for order type Z3NB without any line deletions. |
Outputs and document data match current multi WL process |
| SNC004 |
end to end cycle for order type Z3NB without any line deletions for large POs. |
Outputs and document data match current multi WL process |
| SNC005 |
Mass Update Program - Validate it works for all non deleted lines only. |
Outputs and document data match current multi WL process |
| SNC006 |
Work list creation program - Validate it only creates WL for first active item. |
Outputs and document data match current multi WL process |
| SNC007 |
end to end cycle for order type NB-TAB without any line deletions. |
Outputs and document data match current multi WL process |
| SNC008 |
end to end cycle for order type NB-TAB without any line deletions for large POs. |
Outputs and document data match current multi WL process |
Create a PO
Move to SNC
Print ECC PO
PO Download ECC
Publish PO
Create INB delivery
Create WO
Publish WO
Create WO WL
Update confirmations till ZN
Copy Status for all lines of PO
Create ASN Per SO (Draft)
Update ZP
Update the Data in ASN and Save draft
Publish ASN (Final)
MIGO the PO
End to end cycle for Z3NB PO:
Create a PO
Move to SNC
Publish PO
Create WO
Publish WO
Create WO WL
Update confirmations till ZN
Copy Status for all lines of PO
Create INB delivery
Pack the INB delivery
Print UCC labels
Update ZP
Create ASN Per SO (Draft)
Update the Data in ASN and Save draft
ZASN Forward (Booking & Shipping)
Publish ASN (Final)
Create PGR for INB Delivery
ASN From PGR
Solution Details
[Provide complete technical details for configuration or programming here]
1. The Program to create Work List for the WO of first active line of a PO
Program: ZNEC_WO_WL_CREATE_SINGLE this will be replace the existing program: ZNEC_WO_WL_CREATE
Input Options:
2. The Program to copy the confirmations to the rest of PO lines.
Program: ZPO_CONFIRMATION (this is a new program)
Input options:
a. Date range input:
The confirmations updated in the range of date on active line of POs are considered and copied to the rest of lines.
b. No. of days input:
The confirmations updated in past X days on active line of POs are considered and copied to the rest of lines.
Issues
[List Issues / Bugs identified in configuration or development]